fix: Enhance WikiMetaClient to handle rate limiting with retries and …#610
Merged
fix: Enhance WikiMetaClient to handle rate limiting with retries and …#610
Conversation
ahmed-arb
force-pushed
the
ahmed-arb/fetch-translations-fix
branch
from
9ad1a87 to
13cb415
Compare
…update sync command to fetch translations from Meta. Improved logging for error handling and response validation.
ahmed-arb
force-pushed
the
ahmed-arb/fetch-translations-fix
branch
from
13cb415 to
8a1dba5
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR improves Meta translation sync reliability by adding retry/backoff handling for rate-limited (429) responses in WikiMetaClient, and updates the sync command to better handle partial failures when fetching translations.
It also improves logging/validation for Meta API responses, so failures are clearer and skipped blocks can be retried safely on future runs.
Related issue: #609